This chapter describes the Remote Program Load (RPL) feature and the Preboot Execution Environment (PXE) feature.
If you are using the IBM Turbo 16/4 Token-Ring PC Card 2, see IBM Turbo 16/4 Token-Ring PC Card 2 RPL feature. Otherwise, see the following information.
RPL is supported on the following PCI adapters:
The adapter supports RPL from the following servers:
PXE is supported by several IBM token-ring PCI adapters.
| Note: | Consult your system administrator for information about whether your server supports PXE. |
PXE is supported on the following adapters:
The RPL feature enables an adapter to boot a computer using files that the computer receives from a LAN server. The computer that requests these files is referred to as the client computer, and the computer that responds with these files is referred to as the LAN server. In order for RPL to take place, two things must occur. First, the RPL feature of the adapter in the client machine initiates the RPL request. Second, a LAN server responds to the RPL request with the files to bring up, or boot, the client computer.
The PCI token-ring adapters support PXE from any server that supports PXE 2.x. You can download the PXE specification from http://developer.intel.com/ial/wfm/wfmspecs.htm.
The following topics are addressed in this section:
For the RPL/PXE process to begin, the feature must be enabled on the adapter installed in the client computer, and the client computer must recognize the RPL/PXE feature of the adapter as the first or only bootable device present.
The adapter is shipped with the RPL/PXE feature enabled. You can ensure that it is enabled by running the diagnostics and, at the diagnostics test panel, pressing F5 to view or change the RPL setting.
All IBM PCs support RPL, and many IBM-compatible PCs also do. If your computer is not an IBM PC, refer to your computer's user's manual or contact the manufacturer if you are not sure whether it supports RPL.
On most IBM PCs you can make this adapter the first bootable, or startup, device by choosing Network as the first startup device in the startup sequence in the configuration utility (usually you enter the configuration utility by pressing F1 when the IBM logo and Configuration Utility program symbol appear during the power-on process). If drive A is the first bootable device, consider making the adapter the second bootable device. Refer to the user's manual for your IBM PC if you need further instructions for altering the startup sequence or entering the configuration utility.
Many non-IBM machines and some older IBM machines do not have a configuration utility, or do not allow a choice of a network-bootable device in the configuration utility. On these machines you can either remove the hard disk or use the RPLENABL.EXE utility program provided with this adapter in the RPLPKG.EXE package on the CD-ROM to disable the hard disk as a bootable device. After the hard disk is disabled as a bootable device, computers that support RPL adapters will attempt to boot from the network as long as no diskette is in the diskette drive.
The procedure for changing the boot protocol depends on your adapter's microcode level. To determine your adapter's microcode level, look at the AL- field displayed on the DHCP/PXE or RPL screen. There are two fields displayed, such as AL-00001 ALB1BG2.
If the second field has only six digits, or if the seventh digit is "1", as shown in the following examples, the microcode supports PXE 1.
AL-00001 PX10AH AL-00001 ALB1BG1
If the seventh digit is "2", as shown in the following example, the microcode supports PXE 2.
AL-00001 ALB1BG2
The following adapters ship with PXE 1:
A PXE 2 flash update is available for these adapters at http://www.ibm.com/networking/support.
For the procedure to change the boot protocol, see Changing the boot protocol (PXE 1.x).
The following adapters ship with PXE 2:
A PXE 1 flash update is available at http://www.ibm.com/networking/support.
For the procedure to change the boot protocol, see Changing the boot protocol (PXE 2.x).
If the microcode on your adapter is flashed to support PXE 1.x, use the following procedure to change the boot protocol. If the microcode on your adapter is flashed to support PXE 2.x, see Changing the boot protocol (PXE 2.x).
After you select RPL as the first startup, or boot, device you will see a DHCP panel when your client machine is booting. By default, the adapter will first try Dynamic Host Configuration Protocol (DHCP) as the first protocol. Any time before the client has connected to the DHCP server, you can press Alt+S to switch to RPL. The following figure is an example of the DHCP panel:
+--------------------------------------------------------------------------------+ | IBM PCI Token-Ring DHCP | | ET-02:15:36 | | ID-268 0030 | | BU-0000 | | AA-0004AC570001 | | AL-000001 PX10AH | | BL-CD0110 | | RM-C800 | | OP-0000 16 | | | | DD-0002 | | AR- | | DR- | | XR- | | TR- | | AC-8C00 00002000 8820 | | AE-000 OP-0011 | | Press ALT-S to switch to RPL | | Press ESC to return to BIOS | | Ending DHCP | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | IBM PCI Token-Ring RPL | | ET-02:15:36 | | ID-268 0030 | | BU-0000 | | AA-0004AC570001 | | AL-000001 PX10AH | | BL-CR1.0243 | | RM-C800 | | OP-0000 16 | | | | RQ-000F | | SF- | | SN- | | RS-2010 | | PC-0606 | | AC-8C00 00002000 8820 | | AE-000 OP-0011 | | Press ALT-S to switch to DHCP | | Press ESC to return to BIOS | | Ending RPL | +--------------------------------------------------------------------------------+
This example shows all of the possible error and status message prefixes. You will normally not see the error status condition prefixes, such as PC-, unless an error condition occurs. These error and status messages are described in RPL messages.
If the microcode on your adapter is flashed to support PXE 2.x, use the following procedure to change the boot protocol. If the microcode on your adapter is flashed to support PXE 1.x, see Changing the boot protocol (PXE 1.x).
Current operating system software installation programs either require your attendance in order to enter information in response to system prompts (attended installation) or do not require your attendance (unattended installation). To accommodate this mix of attended versus unattended, a menu in the Token Ring Option ROM is provided to guide you in setting up your Token Ring Option ROM.
You can access the menu at Option ROM initialization time. Use this menu to change the protocol (RPL or PXE) and the protocol's behavior if the protocol fails to reach a boot server of the selected protocol or if the initial bootstrap returns control to the boot ROM code.
At option ROM initialization time, the following line is displayed:
+--------------------------------------------------------------------------------+ |Token-Ring ROM Initializing...... | +--------------------------------------------------------------------------------+
After the line appears, you have 5 seconds to press Ctrl+S to access the PCI Token Ring's boot protocol/protocol failure menu, as shown in the following example. If you do not press Ctrl+S within five seconds, the PCI token-ring's option ROM settings remain unchanged and the system boot continues.
If you press Ctrl+S within five seconds, the following options are displayed:
+--------------------------------------------------------------------------------+ |Token-Ring ROM Initializing...... | |1 PXE/Local Boot <<<< Current Mode | |2 PXE only | |3 RPL/Local Boot | |4 RPL only | |5 Local Boot | |ESC-No Change | +--------------------------------------------------------------------------------+
| Note: | <<<< Current Mode displayed beside an option indicates the current adapter setting. If you change the setting, <<<< Current Mode will display next to the new option the next time you reboot your system. |
The options are described in the following table:
| Option | Description |
|---|---|
| 1 PXE/Local Boot | Use the PXE protocol. If the PXE protocol fails, or the initial downloaded bootstrap returns control to the token-ring adapter's boot ROM code, the boot ROM code will return control back to BIOS, and onto the next boot device. |
| 2 PXE only | Use the PXE protocol. If the PXE protocol fails, or the initial downloaded bootstrap returns control to the token-ring adapter's boot ROM code, the boot ROM code will retry the PXE protocol. This will continue indefinitely. |
| 3 RPL/Local Boot | Use the RPL protocol. If the RPL protocol fails, or the initial downloaded bootstrap returns control to the token-ring adapter's boot ROM code, the boot ROM code will return control back to BIOS, and onto the next boot device. |
| 4 RPL only | Use the RPL protocol. If the RPL protocol fails, or the initial downloaded bootstrap returns control to the token-ring adapter's boot ROM code, the boot ROM code will retry the RPL protocol. This will continue indefinitely. |
| 5 Local Boot | This option informs BIOS that this option ROM is not an IPL device, and therefore the option ROM will not be called to execute its boot protocol. |
| ESC | The current boot protocol or protocol failure is unchanged. |
Select an option by pressing the option's number on the number row on your keyboard or on the numeric keypad (with the NumLock function enabled). The display confirms your selection.
Remember the following key points:
If you select 1 PXE/Local Boot or 2 PXE only, a series of panels appear. The first panel appears during the initialization and opening of the adapter onto the ring.
+--------------------------------------------------------------------------------+ | PCI Token-Ring PXE CS2| |ET-00:00:00 016| |ID-2460 068 | |BU-0000 | |AA-00112233445566 | |AL-000001 PX14CN2 | |BL-CS200 | |RM-C800 | |OP-0000 0016 | | | | | | | | | | | | | | | | | | | |RS-2010 | |AC/PC-0606 | |AE-000 OP-0011 | | | +--------------------------------------------------------------------------------+
The second panel appears after the adapter successfully opens onto the ring and starts the PXE/DHCP protocol.
+--------------------------------------------------------------------------------+ | PCI Token-Ring PXE CS20| |ET-00:00:00 016M| |UU-11223344556677889900112233445566 IP-17.17.17.2 | |DD-0001 SM-255.255.255.0 | |AR-0002 DHCPSvr-10.10.10.3 | |DR-0001 Router-17.17.17.8 | |XR-0001 SR1-0.0.0.0 | | SR2-0.0.0.0 | | BINL-10.10.10.5 | | | | | | | |TF- TFTP IP-10.10.10.5 TFTPGW-17.17.17.8 | |c:\path\filename.ext | |Press space bar to suspend NBP download | | | | | | | | | |RS-2010 | |AC/PC-0606 | |AE-000 OP-0011 | +--------------------------------------------------------------------------------+
The third panel appears if the boot server has provided a PXE Boot menu giving you the option of which boot server to use.
+--------------------------------------------------------------------------------+ | PCI Token-Ring PXE CS20| |ET-00:04:10 016M| |Select Boot Server 10 IP-17.17.17.2 | |Local Boot SM-255.255.255.0 | |Bootserver 1 DHCPSvr-10.10.10.3 | |Bootserver 2 Router-17.17.17.8 | | SR1-0.0.0.0 | | SR2-0.0.0.0 | | BINL-10.10.10.5 | | | | | |BD-0001 BootSrv-10.10.10.4 | |TF-0001 TFTP IP-10.10.10.5 TFTPGW-17.17.17.8 | |c:\path\filename.ext | |Press space bar to suspend NBP download 3 | |BIS-21 | | | | | | | |RS-2010 | |AC/PC-0606 | |AE-000 OP-0011 | +--------------------------------------------------------------------------------+
If you select 3 RPL/Local Boot or 4 RPL only, the following panel appears.
+--------------------------------------------------------------------------------+ | PCI Token-Ring RPL | | ET-00:15:36 | | ID-268 0030 | | BU-0000 | | AA-0004AC570001 | | AL-000001 PX14CN2 | | BL-CS200 | | RM-C800 | | OP-0000 0016 | | RQ-000F | | SF- | | SN- | | RS-2010 | | PC-0606 | | AC-8C00 00002000 8820 | | AE-000 OP-0011 | | | +--------------------------------------------------------------------------------+
The example panels show all of the possible error and status message prefixes. You will normally not see the error status condition prefixes, such as PC-, unless an error condition occurs. These error and status messages are described in RPL messages.
This manual assumes that you have already set up your OS/2 LAN Server for RPL and installed the DOS or OS/2 RPL image. If you have not, refer to the OS/2 LAN Server documentation and install RPL support before installing RPL support for the adapter on the OS/2 LAN Server. In summary, at this point you should have already performed the following steps:
Use the OS/2 syslevel command on your OS/2 LAN Server to check the CSD level.
After these steps are complete, run the following steps on the OS/2 LAN Server to add RPL support for the adapter:
| Client Operating Environment | Record Identifier |
|---|---|
| OS/2 3.0 | R_230_DTKTRP |
| DOS | R_DTKTRP_NDIS |
The following steps are a sample procedure for creating a NetWare Client boot image:
Place the following files on the bootable DOS diskette:
LSL.COM AUTOEXEC.BAT CONFIG.SYS NET.CFG VLM.EXE IBMTRPO.EXE ROUTE.COM IPXODI.COM REDIR.VLM CONN.VLM SECURITY.VLM NWP.VLM PRINT.VLM IPXNCP.VLM NDS.VLM FIO.VLM NETX.VLM TRAN.VLM BIND.VLM GENERAL.VLM
Your CONFIG.SYS file should have the following statements:
REM Use the DOS= and DEVICE= statements if you want to use high memory and XMS memory. REM DOS=HIGH REM DEVICE=A:\HIMEM.SYS REM DEVICE=A:EMM386.EXE NOEMS FILES=40 BUFFERS=20 LASTDRIVE=Z
Your AUTOEXEC.BAT file should have the following statements:
PATH A:\ SET NWLANGUAGE=ENGLISH LSL IBMTRPO ROUTE IPXODI REM If you issue commands that reload COMMAND.COM, REM you must also copy COMMAND.COM REM to the NetWare Server \system directory and REM uncomment the COMSPEC command statement below. REM SET COMSPEC=F:\SYSTEM\COMMAND.COM VLM LOGIN yourID
Place the following files on the bootable DOS diskette:
IBMTRPO.EXE AUTOEXEC.BAT LSL.COM NETX.EXE ROUTE.COM IPXODI.COM NET.CFG
Your AUTOEXEC.BAT should have the following statements:
PATH A:\ LSL IBMTRPO ROUTE IPXODI REM If you issue commands that reload COMMAND.COM, REM you must also copy COMMAND.COM REM to the NetWare Server \system directory and REM uncomment the COMSPEC command statement below. REM SET COMSPEC=F:\SYSTEM\COMMAND.COM NETX F: LOGIN yourID
Following is a sample of the NET.CFG file for VLM or NETX clients:
Link Driver IBMTRPO
FRAME TOKEN-RING MSB
DATARATE AUTO
RXBUFFERS 9
TXBUFFERS 1
NetWare DOS Requester
FIRST NETWORK DRIVE = F
NETWARE PROTOCOL = NDS BIND
load rpl bind rpl to <driver>where <driver> is the token-ring driver loaded on your NetWare Server.
Refer to the chapter on Remoteboot in the Microsoft Windows NT Networking Guide for the following features:
At a command prompt on the server, change to the c:\winnt\RPL\bblock\netbeui directory and create a directory named ibmtrp. Within the ibmtrp subdirectory create a PROTOCOL.INI file that has the following data in it:
[protman] drivername = protman$ dynamic = yes priority = netbeui [netbeui_xif] drivername = netbeui$ bindings = ibmtrp_nif names = 6 ncbs = 12 packets = 20 pipeline = 10 sessions = 6 stacksize = 512 lanabase = 0 [xnsnb_xif] drivername = xnsnb$ bindings = ibmtrp_nif load = xnsnb[cbr] lanabase = 1 [xnstp_xif] drivername = xnstp$ bindings = ibmtrp_nif load = xnstp[ub] lanabase = 1 [tcpip_xif] drivername = TCPIP$ disabledhcp = (TCPIP_NO_DHCP) ipaddress0 = (TCPIP_ADDRESS) subnetmask0 = (TCPIP_SUBMASK) defaultgateway0 = (TCPIP_GATEWAY) tcpsegmentsize = 1450 tcpwindowsize = 1450 nbsessions = 6 load = tcptsr[c],tinyrfc[c],emsbfr[cr] unload = "unloadt /notsr[dc]" bindings = ibmtrp_nif lanabase = 1 [ipx_xif] drivername = ipx$ load = ipxmark[u],ipx[u] unload = ipxrel[c] bindings = ibmtrp_nif lanabase = 1 [msdlc_xif] drivername = msdlc$ bindings = ibmtrp_nif load = msdlc[ub] unload = msdlc[u] [ibmtrp_nif] drivername = ibmtrp$ MaxTransmits = 2 MaxTxFrameSize = 2048 MinRcvBuffs = 8 RcvBuffSize = 1120
Also, within that same subdirectory ibmtrp create a DOSBB.CNF file that has the following data in it:
;DOS RPL with IBM PCI Token-Ring Adapter BASE CCH RPL BBLOCK\RPLBOOT.SYS LDR BBLOCK\RPLSTART.COM ~ DAT BBLOCK\NETBEUI\IBMTRP\PROTOCOL.INI ;DAT BBLOCK\NDIS\IBMTRP\LA1.MSG DRV BBLOCK\RPLDISK.SYS ~ ~ EXE BBLOCK\RPLPRO1.COM ~ 2 ~ EXE BBLOCK\I13.COM ~ ~ ~ EXE BBLOCK\RPLBIND2.EXE ~ ~ EXE BBLOCK\PROTMAN.EXE ~ ~ EXE BBLOCK\RPLBIND1.EXE ~ ~ ;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~ ;DRV BBLOCK\TCPDRV.DOS /IDOS ~ ~ EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~ DRV BBLOCK\NDIS\IBMTRP.DOS /NOMSG 22 ~ DRV BBLOCK\PROTMAN.DOS /IDOS ~ M
Go to http://www.ibm.com/networking/support
and download the IBM PCI Token-Ring Adapter driver diskette. Copy the
following files from the DOS directory (a:\dos) to
c:\winnt\rpl\bblock\ndis:
IBMTRP.DOS
LA1.MSG
The Windows NT 4.0 Server support for RPL does not include the image for IBM DOS.
| Note: | If the DOS image is already on the server, skip to Creating Remoteboot configurations for the PCI token-ring adapters. |
Copy c:\dos\*.* v:\binfiles\dos700 Attrib -s -h c:\io.sys Attrib -s -h c:\msdos.sys Copy c:\io.sys v:\binfiles\dos700 Copy c:\msdos.sys v:\binfiles\dos700 Attrib +s +h c:\io.sys Attrib +s +h c:\msdos.sys
From a command prompt on the server, run RPLCMD.EXE. This utility allows you to add boot block records for the adapter and vendor ID. Use the following illustration to set up and configure a boot image for your adapter.
c:\> rplcmd
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=DOS700 **rpl client environment**
VendorName=002035 **the first 6 digits of the adapter's hexadecimal MAC address**
BbcFile=bblock\netbeui\ibmtrp\dosbb.cnf
All other parameters are optional
BootComment=DOS 700 IBM PCI TOKEN RING
WindowSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quit]: v
Add Del Enum: a
VendorName=002035 **the first 6 digits of the adapter's hexadecimal MAC address**
VendorComment=DOS 700 IBM PCI TOKEN RING
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=DOS700C
BootName=DOS700
DirName=DOS
DirName2=DOS700
FitShared=fits\dos700.fit
FitPersonal=fits\dos700p.fit
All other parameters are optional
ConfigComment=DOS 700 IBM PCI TOKEN RING ** Shown in step 4 below **
DirName3=
DirName4=
Adapter Boot Config Profile Service Vendor Wksta [Quit]: q
| ET-00:00:45 |
Explanation: Elapsed Time. A continuously updated field indicating the elapsed time since the RPL feature gained control. |
| ID-268 BBDF |
Explanation: Identification. An indication of which adapter is using the RPL feature. 268 indicates a PCI token-ring adapter. BBDF indicates the PCI bus, device, and function number for the PCI slot in which the adapter is inserted. |
| BU-0000 |
Explanation: Bring-Up. This field is displayed as X'0000' if the adapter has been successfully initialized and opened. If not, a code other than X'0000' is displayed and the field is highlighted. See Troubleshooting RPL problems. |
| AA-08005A2B0000 |
Explanation: Adapter address. The permanently encoded address of the token-ring adapter in your computer. This address is always 12 hexadecimal characters (6 bytes) long. |
| AL-000001 PX10AH |
Explanation: Adapter Level. The Engineering Change (EC) level of the code on the token-ring adapter. |
| BL-CD0106 |
Explanation: BIOS Level (module level). The EC level of the code in the RPL feature. |
| RM-CC00 |
Explanation: Memory (read-only memory). Segment address in memory where BIOS has placed the RPL ROM. |
| OP-0000 0004 |
Explanation: Open Return Code. The first 4 digits are X'0000' and the last 4 digits identify the adapter data rate, if the adapter has been successfully opened and attached to the network. If not, a code other than X'0000' is displayed and the field is flashing. See Troubleshooting RPL problems. |
| RQ-0001 |
Explanation: Request Count (FIND Frame Count). The number in hexadecimal of FIND frames that have been transmitted. An excessive request count indicates that the LAN server is not present, is congested, or is not correctly configured to RPL this adapter. |
| SF-0001 |
Explanation: SEND.FILE.REQUEST Frame Count. The number of SEND.FILE.REQUEST frames that have been transmitted. An excessive SEND.FILE.REQUEST frame count indicates that the LAN server is not responding after having been found. |
| SN-0023 |
Explanation: File Response Sequence Number. This value is displayed when the LAN server has responded to the SEND.FILE.REQUEST. It indicates how many times valid FILE.DATA.RESPONSE frames have been received. |
| RS-0040 |
Explanation: Ring Status. This field displays a code indicating the status of the network. The field will be highlighted if the operation cannot continue; it will not be highlighted if processing can continue. See Troubleshooting RPL problems. |
| PC-4020 |
Explanation: Computer error. This field displays an error code indicating that the adapter has difficulty in functioning with the computer. In most cases, the panel will be frozen and this field will be highlighted because the adapter cannot continue. See Troubleshooting RPL problems. |
| AC-0040 0000 0000 0000 |
Explanation: Adapter check. The adapter has detected an internal error and cannot continue. Reboot your computer. If this problem persists, record the adapter check code, and contact your network administrator. |
| AE-nnn XX-0011 |
Explanation: Adapter error. The adapter in your computer could not establish communication with the LAN server. The nnn indicates the instance number. The reason for this error is indicated by the XX message to the right of AE-nnn. XX can be either BU or OP. The BU and OP messages are described previously in this section. |
| ET-00:00:45 |
Explanation: Elapsed Time. A continuously updated field indicating the elapsed time since the RPL feature gained control. |
| ID-268 BBDF |
Explanation: Identification. An indication of which adapter is using the RPL feature. 268 indicates a PCI token-ring Adapter. BBDF indicates the PCI bus, device, and function number for the PCI slot in which the adapter is inserted. |
| BU-0000 |
Explanation: Bring-Up. This field is displayed as X'0000' if the adapter has been successfully initialized and opened. If not, a code other than X'0000' is displayed and the field is highlighted. See Troubleshooting RPL problems. |
| AA-08005A2B0000 |
Explanation: Adapter address. The permanently encoded address of the token-ring adapter in your computer. This address is always 12 hexadecimal characters (6 bytes) long. |
| AL-000001 PX10AH |
Explanation: Adapter level. The Engineering Change (EC) level of the code on the token-ring adapter. |
| BL-CD0106 |
Explanation: BIOS level (module level). The EC level of the code in the RPL feature. |
| RM-CC00 |
Explanation: Memory (read-only memory). Segment address in memory where BIOS has placed the RPL ROM. |
| OP-0000 0004 |
Explanation: Open return code. The first 4 digits are X'0000' and the last 4 digits identify the adapter data rate, if the adapter has been successfully opened and attached to the network. If not, a code other than X'0000' is displayed and the field is flashing. See Troubleshooting RPL problems. |
| DD-0001 |
Explanation: DHCP discover count. The number in hexadecimal of DHCP Discover frames that have been transmitted. The field will be highlighted with a value of 0004 10 if the server is not present, is congested, or is not currently configured to respond to DHCP messages. |
| AR-0001 |
Explanation: ARP request count. The number in hexadecimal of ARP Requests broadcasted onto the network. If the field is highlighted as XXXX 00, the client received a reply to its ARP request. Check to see if any other machine is assigned the client's IP address and check the DHCP server's DHCP scope of addresses. |
| DR-0001 |
Explanation: DHCP request count. The number in hexadecimal of DHCP Request packets transmitted to the DHCP server/Proxy DHCP server. The field will be highlighted with a value of XXXX 10 if the server is not present, is congested, or is not correctly configured to respond to DHCP Request messages. |
| XR-0001 |
Explanation: Extended DHCP request count. The number in hexadecimal of Extended (PXE) DHCP Request packets transmitted to the Boot Image Negotiation Layer (BINL) server. The field will be highlighted with a value of XXXX 10 if the server is not present, is congested, or is not correctly configured to respond to Extended (PXE) DHCP Request messages. |
| TF-0009 |
Explanation: TFTP block count. The number in hexadecimal of UDP data packets received during the TFTP of the initial bootstrap program. The field will be highlighted with a value of XXXX 10, indicating a general timeout, if the server is not present or is congested. If the field is highlighted with a value of XXXX 3X, check the path and filename of the initial bootstrap program on the server and check if the server's TFTP program is active. |
| RS-0040 |
Explanation: Ring status. This field displays a code indicating the status of the network. The field will be highlighted if the operation cannot continue; it will not be highlighted if processing can continue. See Troubleshooting RPL problems. |
| PC-4020 |
Explanation: Computer error. This field displays an error code indicating that the adapter has difficulty in functioning with the computer. In most cases, the panel will be frozen and this field will be highlighted because the adapter cannot continue. See Troubleshooting RPL problems. |
| AC-0040 0000 0000 0000 |
Explanation: Adapter check. The adapter has detected an internal error and cannot continue. Reboot your computer. If this problem persists, record the adapter check code, and contact your network administrator. |
| AE-nnn XX-0011 |
Explanation: Adapter error. The adapter in your computer could not establish communication with the LAN server. The nnn indicates the instance number. The reason for this error is indicated by the XX message to the right of AE-nnn. XX can be either BU or OP. The BU and OP messages are described previously in this section. |
| IP-17.17.17.2 |
Explanation: This client's IP address provided by the DHCP server. |
| SM-255.255.255.0 |
Explanation: The subnet mask provided by the DHCP server. |
| DHCPSvr-10.10.10.3 |
Explanation: IP address of the DHCP server. |
| Router-17.17.17.8 |
Explanation: IP address of the router or gateway provided by the DHCP server. |
| SR1-0.0.0.0 |
Explanation: IP address of a static route provided by the DHCP server. |
| SR2-0.0.0.0 |
Explanation: IP address of a static route provided by the DHCP server. |
| BINL-10.10.10.5 |
Explanation: IP address of the Boot Image Negotiation Layer (BINL) service machine. |
| BD-0001 |
Explanation: How many boot server requests sent to the boot server. |
| BootSrv-10.10.10.4 |
Explanation: IP address of the boot server currently being queried for the initial Network Boot Program (NBP) or the IP address of the boot server providing the credentials for NBP authentication. |
| BIS-21 |
Explanation: A highlighted field indicating a Boot Integrity Services error has occurred. |
| Select Boot Server 10 |
Explanation: A list of available boot servers. The prompt is displayed followed by the number of seconds remaining before the first item in the boot menu is auto-selected. If a number is not present, there is no timeout. Use the up and down arrow keys to traverse the menu and press enter to select. |
| TFTP IP-10.10.10.5 |
Explanation: IP address of the server currently being used to download the initial Network Boot Program (NBP). |
| TFTPGW-17.17.17.8 |
Explanation: IP address of the gateway currently being used to download the initial Network Boot Program (NBP). |
If you do not get the expected results when using an RPL feature on a client computer, see Table 1.
If other computers on the network need problem determination, you might need one or more of the following documents:
Table 1. Failure indication messages
| Failure Indication | Action |
|---|---|
| The computer's BASIC panel appears, or the computer boots to the hard disk or diskette drive. | Perform the steps in Installation and configuration. |
| The BU field on the client computer display panel is highlighted. | See Bring-up error. |
| The OP field on the client computer display panel is highlighted. | See Open error. |
| The RS field on the client computer display panel has a value other than zero (0) and is highlighted. | See Ring status error. |
| The PC field on the client computer display panel is highlighted or is shown with counters not being updated. | See PC Error. |
| The client computer display panel shows any response that has not been identified. | Contact your network administrator. |
The client computer display panel shows that the elapsed
time (ET) field has stopped with only a few seconds of time accumulated, and
the bring-up (BU) error field is highlighted. The RPL feature tried
three times and was unable to initialize the adapter for use. The BU
error codes and the action to take are listed in Table 2.
Table 2. Bring-up error causes and actions
| BU Error Code | Cause | Action |
|---|---|---|
| 0020-002F, 0030-003F | A module on the adapter is not responding correctly. | The adapter appears defective. Run the diagnostics. |
| 0048 | Initialize timeout. | The adapter appears defective. Run the diagnostics. |
| All others | Adapter failure | The adapter appears defective. Run the diagnostics. Contact your network administrator if problems persist. |
The open error (OP) field contains an error code. This code might be displayed normally or flashing.
If the error code is flashing, the RPL feature is trying to open the adapter after an unsuccessful attempt.
If the problem persists, record the 4 digits of the flashing OP
field. Using Open Error and the Reason Code as the symptom, refer to
the IBM Token-Ring Network Problem Determination Guide to resolve the problem.
Table 3. Open error causes and actions
| OP Error Code | Cause | Action |
|---|---|---|
| 0011, 0010 | No media attached. | Connect the UTP or STP cable to the adapter. |
| 002D | A client computer is trying to be the first active computer on a token-ring network. | Start your RPL server. If the error persists, reboot the client computer. |
| All others | Adapter open failure. | Refer to the IBM Token-Ring Network Problem Determination Guide. |
A ring error was detected when the RPL feature or bootstrap
program was executing. The ring status (RS) error field contains the
error code. Locate the error code in Table 4 to determine the correct action to take. Some values
might be displayed that are a combination of the values listed in the
table. The x's used in the RS Error Code column can be
any hexadecimal number from 0 through F.
Table 4. Ring status error causes and actions
| RS Error Code | Cause | Action |
|---|---|---|
| Cxxx to Dxxx |
| Refer to the IBM Token-Ring Network Problem Determination Guide. |
| 2000 | This adapter has detected a soft-error condition. | No action required. |
| 08xx | Wire fault. The adapter has detected a problem in itself or in its lobe. | Refer to the IBM Token-Ring Network Problem Determination Guide. |
| 04xx | The adapter detected an internal hardware error. | Contact your network administrator. |
| x1xx | Remove received. This adapter was removed from the network. | Contact your network administrator for assistance. |
| 0080 | Counter overflow. One of the error log counters has incremented past 256. | Restart the computer. |
| 0040 or 0060 | Single station. The adapter has opened and is the only station on the network. This bit resets when another station inserts. | No action is required unless other stations are known to be operating on this network. If other stations are on the network, refer to the IBM Token-Ring Network Problem Determination Guide. |
| 0020 | Ring recovery. The adapter is transmitting or receiving claim token frames. | No action is required. |
| 0004 | Full-duplex. The adapter is operating in full-duplex mode. | No action is required. |
| All others | Reserved. | Contact your network administrator for assistance. |
The RPL feature has detected a problem with either the software
or hardware in the client computer. Retry the operation by restarting
the computer at least once. If the problem persists, locate the error
code in Table 5 to determine the correct action to take.
Table 5. PC error causes and actions
| PC Error Code | Cause | Action |
|---|---|---|
| 05xx | An invalid command control block (CCB) code was issued to the adapter support subset. xx = the CCB code. | Check the bootstrap program if it is user-written. If not, contact your network administrator for assistance. Provide the CCB code. |
| 06xx (not highlighted) | PROGRAM.ALERT frames being transmitted. The xx
portion of the value represents the alert code.
| Restart the computer. If this error persists, contact your network administrator for assistance. |
| 07xx | The adapter failed a wrap test. xx = system status block (SSB) return code. | The adapter appears defective. Run the diagnostics. Contact your network administrator if problems persist. |
| All others | A computer hardware or software error has occurred. | Perform the computer diagnostic test procedure or contact your network administrator for assistance. |
The IBM Turbo 16/4 Token-Ring PC Card 2 supports RPL from the following servers:
The Remote Program Load (RPL) function enables an adapter to boot a computer using files that the computer receives from a LAN server. The computer that requests these files is referred to as the client computer, and the computer that responds with these files is referred to as the LAN server. In order for RPL to take place, two things must occur. First, the RPL feature of the adapter in the client machine initiates the RPL request. Second, a LAN server responds to the RPL request with the files to bring up, or boot, the client computer.
The following sections are included here:
For the RPL process to begin, the feature must be enabled on the adapter installed in the client computer, and the client computer must recognize the RPL feature of the adapter as the first or only bootable device present.
The adapter is shipped with the RPL feature enabled. To ensure that it is enabled, run the diagnostics and, at the diagnostics test panel, press F5 to view or change the RPL setting.
All IBM PCs support RPL, and many IBM-compatible PCs also do. If your computer is not an IBM PC, refer to your computer user manual or contact the manufacturer if you are not sure whether it supports RPL.
On most IBM PCs you can make this adapter the first bootable, or startup, device by selecting Network as the first startup device in the startup sequence in the configuration utility (usually you enter the configuration utility by pressing F1 when the IBM logo and Configuration Utility program symbol appear during the power-on process). If drive A is the first bootable device, consider making the adapter the second bootable device. Refer to the user manual for your IBM PC if you need further instructions for altering the startup sequence or entering the configuration utility.
After you have successfully selected RPL as the first startup, or bootable, device you will see an RPL panel when your client computer is booting.
+--------------------------------------------------------------------------------+ |IBM Turbo 16/4 T-Ring PC Card RPL v1.01 (980921) | |(C) Copyright 1991-1994 Novell, Inc. All Rights Reserved. | |(C) Copyright 1996 IBM Corp. All Rights Reserved. | | | |RPL-ROM-HSM: 200 BU-0000 | |RPL-ROM-HSM: 201 OP-0000 16 | | | |RPL-ROM-ADR: 0020 3556 6D87 | |RPL-ROM-IRQ: 2 | |RPL-ROM-MM1: D600 | |RPL-ROM-PIO: 0A20 | | | |RPL-ROM-FFC: 01 | |RPL-ROM-SFC: 02 | |RPL-ROM-SEQ: 01 | |RPL-ROM-ERR: | +--------------------------------------------------------------------------------+
This example shows all of the possible error and status message prefixes. You will normally not see the error status condition prefixes, such as RPL-ROM-ERR, unless an error condition occurs. These error and status messages are described in RPL messages.
Please refer to the chapter on Remoteboot in the Microsoft Windows NT Networking Guide for the following features:
At a command prompt on the server, change to the c:\winnt\RPL\bblock\netbeui directory and create a directory named ibmtokcs. Within the ibmtokcs subdirectory create a PROTOCOL.INI file that has the following data in it:
| Note: | Even though the DOS device driver file is called IBMTOKCS, the device driver
is known to the operating system as IBMTOK.
[protman] drivername = protman$ dynamic = yes priority = netbeui [netbeui_xif] drivername = netbeui$ bindings = ibmtok_nif names = 6 ncbs = 12 packets = 20 pipeline = 10 sessions = 6 stacksize = 512 lanabase = 0 [xnsnb_xif] drivername = xnsnb$ bindings = ibmtok_nif load = xnsnb[cbr] lanabase = 1 [xnstp_xif] drivername = xnstp$ bindings = ibmtok_nif load = xnstp[ub] lanabase = 1 [tcpip_xif] drivername = TCPIP$ disabledhcp = (TCPIP_NO_DHCP) ipaddress0 = (TCPIP_ADDRESS) subnetmask0 = (TCPIP_SUBMASK) defaultgateway0 = (TCPIP_GATEWAY) tcpsegmentsize = 1450 tcpwindowsize = 1450 nbsessions = 6 load = tcptsr[c],tinyrfc[c],emsbfr[cr] unload = "unloadt /notsr[dc]" bindings = ibmtok_nif lanabase = 1 [ipx_xif] drivername = ipx$ load = ipxmark[u],ipx[u] unload = ipxrel[c] bindings = ibmtok_nif lanabase = 1 [msdlc_xif] drivername = msdlc$ bindings = ibmtok_nif load = msdlc[ub] unload = msdlc[u] [ibmtok_nif] drivername = ibmtok$ MaxTransmits = 2 MaxTxFrameSize = 2048 MinRcvBuffs = 8 RcvBuffSize = 1120 |
Also, within that same subdirectory ibmtokcs create a DOSBB.CNF file that has the following data in it.
;DOS RPL with IBM Turbo 16/4 Token-Ring Adapter BASE 1A0H RPL BBLOCK\RPLBOOT.SYS LDR BBLOCK\RPLSTART.COM ~ DAT BBLOCK\NETBEUI\IBMTOKCS\PROTOCOL.INI ;DAT BBLOCK\NDIS\IBMTOKCS\LA1.MSG DRV BBLOCK\RPLDISK.SYS ~ ~ ~ EXE BBLOCK\RPLPRO1.COM ~ 2 ~ EXE BBLOCK\I13.COM ~ ~ ~ EXE BBLOCK\RPLBIND2.EXE ~ ~ EXE BBLOCK\PROTMAN.EXE ~ ~ EXE BBLOCK\RPLBIND1.EXE ~ ~ ;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~ ;DRV BBLOCK\TCPDRV.DOS /IDOS ~ ~ EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~ DRV BBLOCK\NDIS\IBMTOKCS.DOS DRV BBLOCK\PROTMAN.DOS /IDOS ~ M
Go to http://www.ibm.com/networking/support
and download the IBM Turbo 16/4 Token-Ring Adapter driver diskette.
Copy the following files from the DOS directory (a:\dos) to
c:\winnt\rpl\bblock\ndis:
IBMTOKCS.DOS
LA1.MSG
The Windows NT 4.0 Server support for RPL does not include the image for IBM DOS.
| Note: | If the DOS image is already on the server, skip to Creating Remoteboot configurations for the IBM Turbo 16/4 Token-Ring Adapter. |
Copy c:\dos\*.* v:\binfiles\dos700 Attrib -s -h c:\io.sys Attrib -s -h c:\msdos.sys Copy c:\io.sys v:\binfiles\dos700 Copy c:\msdos.sys v:\binfiles\dos700 Attrib +s +h c:\io.sys Attrib +s +h c:\msdos.sys
From a Windows NT 4.0 Remoteboot server command prompt, run RPLCMD.EXE. This utility allows you to add boot block records for the adapter and vendor ID. Follow the illustration below to set up and configure a boot image for your adapter.
c:\> rplcmd
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=DOS700 **rpl client environment**
VendorName=002035 **the first 6 digits of the adapter's hexadecimal MAC address**
BbcFile=BBLOCK\NETBEUI\IBMTOKCS\DOSBB.CNF
All other parameters are optional
BootComment=DOS 700 IBM TURBO 16/4 TOKEN RING
WindowSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quit]: v
Add Del Enum: a
VendorName=002035 **the first 6 digits of the adapter's hexadecimal MAC address**
VendorComment=DOS 700 IBM TURBO 16/4 TOKEN RING
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=DOS700C
BootName=DOS700
DirName=DOS
DirName2=
FitShared=fits\dos700.fit
FitPersonal=fits\dos700p.fit
All other parameters are optional
ConfigComment=DOS 700 IBM TURBO 16/4 TOKEN RING ** shown in step 4 below **
DirName3=
DirName4=
Adapter Boot Config Profile Service Vendor Wksta [Quit]: q
| RPL-ROM-HSM: BU-0000 |
Explanation: Bring-Up. This field is displayed as X'0000' if the adapter has been successfully initialized. If not, a code other than X'0000' is displayed and the field is highlighted. See Troubleshooting RPL problems. |
| RPL-ROM-HSM: OP-0000 16 |
Explanation: Open Return Code. The first 4 digits are X'0000' and the last 2 digits identify the adapter data rate, if the adapter has been successfully opened and attached to the network. If not, a code other than X'0000' is displayed and the field is flashing. See Troubleshooting RPL problems. |
| RPL-ROM-ADR: 0020 3556 6D87 |
Explanation: Adapter Address. The permanently encoded address of the token-ring adapter in your computer. This address is always 12 hexadecimal characters (6 bytes) long. |
| RPL-ROM-IRQ: 2 |
Explanation: Interrupt. The system interrupt level that the adapter currently occupies. |
| RPL-ROM-MM1: D600 |
Explanation: Memory (read-only memory). Segment address in memory where BIOS has mapped the RPL ROM code. |
| RPL-ROM-MM2: D800 |
Explanation: Memory (random-access memory). Segment address in memory where BIOS has mapped the token-ring adapter's RAM. |
| RPL-ROM-PIO: 0A20 |
Explanation: System I/O address. The I/O address that the adapter currently occupies in the system. |
| RPL-ROM-FFC: 01 |
Explanation: Request Count (FIND Frame Count). The number (in hexadecimal) of FIND frames that have been transmitted. An excessive request count indicates that the LAN server is not present, is congested, or is not correctly configured to RPL this adapter. |
| RPL-ROM-SFC: 02 |
Explanation: SEND.FILE.REQUEST Frame Count. The number of SEND.FILE.REQUEST frames that have been transmitted. An excessive SEND.FILE.REQUEST frame count indicates that the LAN server is not responding after having been found. |
| RPL-ROM-SEQ: 01 |
Explanation: File Response Sequence Number. This value is displayed when the LAN server has responded to the SEND.FILE.REQUEST. It indicates how many times valid FILE.DATA.RESPONSE frames have been received. |
| RPL-ROM-ERR: |
Explanation: Computer error. This field displays an error code indicating that the adapter has difficulty in functioning with the computer. In most cases, the panel will be frozen and this field will be highlighted because the adapter cannot continue. See Troubleshooting RPL problems. |
The following chart is helpful if you do not get the expected results when you use an RPL feature on a client computer.
If other computers on the network need problem determination, you might need one or more of the following documents:
Table 6. Failure indication messages
| Failure Indication | Action |
|---|---|
| The computer's BASIC panel appears, or the computer shows a diagram to insert a diskette into the diskette drive, or boots to the hard disk or diskette drive. | Perform the installation steps for your adapter. |
| The BU field on the client computer display panel is not X'0000'. | See Bring-up error. |
| The OP field on the client computer display panel is not X'0000'. | See Open error. |
| The Client computer display panel shows any response that has not been identified. | Contact your network administrator. |
The bring-up (BU) field is not X'0000'. The
RPL feature is unable to initialize the adapter for use. The BU error
codes and the action to take are listed here:
| BU Error Code | Cause | Action |
|---|---|---|
| 0020-002C | A module on the adapter is not responding correctly. | The adapter appears to be defective. Run the adapter diagnostics. |
| 0048 | Initialization timeout. | The adapter appears to be defective. Run the adapter diagnostics. |
| All others. | Adapter failure. | The adapter appears to be defective. Run the adapter diagnostics. Contact your network administrator if problems persist. |
The open error (OP) field contains an error code.
If the OP field is not X'0000', the RPL feature is trying to open the
adapter after an unsuccessful attempt. If the problem persists, record
the 4 digits of the OP field. Using Open Error and the Reason Code as
the symptom, refer to the IBM Token-Ring Network Problem Determination
Guide to resolve the problem.
| OP Error Code | Cause | Action |
|---|---|---|
| 0011, 0010 | No media attached. | Connect the cable to the adapter or to the token-ring concentrator or both. |
| 002D | The adapter detected that it was the only adapter present in the ring during the open command it it has removed itself from the ring. | Start your RPL server. If the error persists, reboot the client computer. |
| 002E | The adapter could not detect frames during the open command and has removed itself from the ring. This indicates that either the adapter is running at the wrong speed and does not have circuitry to detect it, or there is something wrong with the access unit or cabling to which the adapter is connected. | Connect the cable to the adapter or to the token-ring concentrator or both. Check if you are using the correct cable. |
| All Others | Adapter open failure. | Refer to the IBM Token-Ring Network Problem Determination Guide. |